I recently bought this computer (sorry for hyperlink, but it is much easier than trying to list all the components):

http://www.newegg.com/Product/Product.aspx?Item=N82E16883227593

I added a Samsung 840 EVO 250gb SSD to it, and then I attempted to do a clean install of windows 8.1 onto the SSD from the reinstall DVD that came with the system. Windows 8.1 appears to install correctly, but when the computer restarts to load windows for the first time, I get a BSoD with the error "attempted execute of noexecute memory". I tried reinstalling, but got the same error.

Note that for testing purposes, I installed windows 7 on the SSD, and it works great. Unfortunately, I do not have a windows 7 key, so this is only a temporary solution. I would like to figure out how to get windows 8.1 on the SSD and running on the my computer.

Thank you in advance for any help or advice that you can give me.

Here are the minidump files if helpful:

 https://drive.google.com/file/d/0B1fPQ--DwbjOV2ZuT0xoeWR6QXc/view?usp=sharing
 https://drive.google.com/file/d/0B1fPQ--DwbjOOUtrWUhfZmRMM1E/view?usp=sharing

• Edited by pacifist0rz Thursday, December 04, 2014 11:19 AM

It appears to be relating to the Wireless LAN. From the photos on the newegg page, it looks like there is no actual wireless card and that it is a built in function. Is this something you are actively using or are you using Ethernet instead? I would see if it is possible to disable the wireless in the BIOS prior to installing Windows 8.1.

Here is the driver name: rtwlanu.sys

• Edited by Tripredacus Thursday, December 04, 2014 5:46 PM

Thank you for the reply.

The wireless USB adapter is definitely the problem.  When I unplug the adapter, windows 8 boots fine.

In fact when i plug it in after windows 8 boots, I immediately get a BSoD.

So now I have a slightly less annoying problem in that my wireless USB adapter doesn't work, but at least we have windows 8 working now.

P

These were Related to RTL8192cu.sys USB NDIS Driver from Realtek Semiconductor Corporation  I would remove the current driver and install the newest driver available

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\120414-8515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*f:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*f:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff801`1981d000 PsLoadedModuleList = 0xfffff801`19ae49b0
Debug session time: Thu Dec  4 05:16:31.298 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:12.923
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {ffffd000217aaa00, 8000000104112963, ffffd000217aa7a0, 2}

*** WARNING: Unable to verify timestamp for rtwlanu.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys
Probably caused by : rtwlanu.sys ( rtwlanu+10d69a )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffd000217aaa00, Virtual address for the attempted execute.
Arg2: 8000000104112963, PTE contents.
Arg3: ffffd000217aa7a0, (reserved)
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  ffffd000217aa7a0 -- (.trap 0xffffd000217aa7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd000217aaa08 rbx=0000000000000000 rcx=ffffe00003734a70
rdx=ffffd000217aa9f0 rsi=0000000000000000 rdi=0000000000000000
rip=ffffd000217aaa00 rsp=ffffd000217aa938 rbp=ffffd000217aa9a8
 r8=ffffd000217aaa00  r9=ffffd000217aa9f8 r10=ffffd00020640000
r11=ffffd000217aa940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ffffd000`217aaa00 0000            add     byte ptr [rax],al ds:ffffd000`217aaa08=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801199c3e32 to fffff8011996d0a0

STACK_TEXT:  
ffffd000`217aa578 fffff801`199c3e32 : 00000000`000000fc ffffd000`217aaa00 80000001`04112963 ffffd000`217aa7a0 : nt!KeBugCheckEx
ffffd000`217aa580 fffff801`19853bc6 : 80000001`04112963 00000000`00000000 ffffd000`217aa720 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x468a2
ffffd000`217aa5c0 fffff801`19885ffd : 00000000`00000008 ffffe000`02759880 ffffd000`217aa7a0 ffffe000`052a0000 : nt!MiSystemFault+0xaf6
ffffd000`217aa660 fffff801`1997732f : 00000000`00000008 ffffe000`03734a70 00000000`00000000 ffffd000`217aa7a0 : nt!MmAccessFault+0x7ed
ffffd000`217aa7a0 ffffd000`217aaa00 : fffff800`01db969a ffffe000`03734a70 ffffe000`03000000 00000000`00000001 : nt!KiPageFault+0x12f
ffffd000`217aa938 fffff800`01db969a : ffffe000`03734a70 ffffe000`03000000 00000000`00000001 00000000`00000000 : 0xffffd000`217aaa00
ffffd000`217aa940 ffffe000`03734a70 : ffffe000`03000000 00000000`00000001 00000000`00000000 ffffd000`217aaa08 : rtwlanu+0x10d69a
ffffd000`217aa948 ffffe000`03000000 : 00000000`00000001 00000000`00000000 ffffd000`217aaa08 fffff800`01ccf62e : 0xffffe000`03734a70
ffffd000`217aa950 00000000`00000001 : 00000000`00000000 ffffd000`217aaa08 fffff800`01ccf62e 00000000`00000004 : 0xffffe000`03000000
ffffd000`217aa958 00000000`00000000 : ffffd000`217aaa08 fffff800`01ccf62e 00000000`00000004 ffffe000`03000000 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rtwlanu+10d69a
fffff800`01db969a ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  rtwlanu+10d69a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rtwlanu

IMAGE_NAME:  rtwlanu.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51dd743f

FAILURE_BUCKET_ID:  0xFC_rtwlanu+10d69a

BUCKET_ID:  0xFC_rtwlanu+10d69a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_rtwlanu+10d69a

FAILURE_ID_HASH:  {095bf10a-821a-1045-f529-a4601d2cff4f}

Followup: MachineOwner
---------

2: kd> lmvm rtwlanu
start             end                 module name
fffff800`01cac000 fffff800`01ea4000   rtwlanu  T (no symbols)           
    Loaded symbol image file: rtwlanu.sys
    Image path: \SystemRoot\system32\DRIVERS\rtwlanu.sys
    Image name: rtwlanu.sys
    Timestamp:        Wed Jul 10 10:48:31 2013 (51DD743F)
    CheckSum:         001EE009
    ImageSize:        001F8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I have to log in my account and say thanks to you. You save my time and life! I bought my desktop and SSD exactly same as pacifist0rz's and got that error. When i remove Wireless USB adapte, the desktop won't carsh. Once again, thank you very much.

Sorry about my bad English grammar :) 

Happy to help.